3 subject="""comment 15"""
4 date="2023-07-15T16:09:46Z"
6 My current thinking is that when a repository does not have a preferred
7 content expression, a content sync could avoid adding content to it.
9 This would avoid surprising behavior after the transition, except for
10 repositories that did at some time have a preferred content expression set,
11 but one that no longer reflects the use of the repository.
13 However, current users of `sync --content` (or of annex.synccontent) do
14 expect it to fill their repositories that don't have preferred content
15 configured. So would a sync that defaults to content syncing then need to
16 behave differently than an explicit `sync --content`? Or should changing
17 behavior in that case also be part of the transition?